[pull] main from liveblocks:main - #305

…d authoritative position on duplicate CREATE ops (PR 1779)

When a client reconnects after losing the server's ack, it re-sends any
still-pending ops. For a `LiveList` push, the server had already stored
the node, so the re-sent CREATE was silently ignored with a bare ack.
The client's local position prediction for that pushed item was never
corrected, causing permanent divergence.

Now, when the server detects a duplicate CREATE with `intent: "push"` on
a node whose parent is a LIST, it returns a new `rectified` outcome
instead of bare-ignoring it: an ack echo carrying the stored
authoritative `parentKey` plus a `SET_PARENT_KEY` fix op, so the
originating client can reconcile its optimistic local position. The
`rectified` reply goes only to the sender; others already saw the op
when it was originally accepted.

Original commit: c4f7f0051a63a0b9225176902bc77e38663294bc